Document management systems and methods

ABSTRACT

A system for managing files over a network comprises a first computer hosting managed folders and files and one or more second computers. The first computer comprises database management software, server software such as server pipe software, and a first unique token. The second computer comprises a software module adapted and configured to be integrated into application software, client software such as client pipe software, and a second unique token. The computers communicate in part using the server and client software to establish a secure session for file access and transfer between the first and second computers.

FIELD OF THE INVENTION

The inventions described herein relate to computer file managementsystems, more specifically to computer data and document files, allowingaccess in a secure and protected manner and allowing for rapid locationand retrieval of such files.

BACKGROUND

Network appliances, such as a network attached storage (NAS) device,have been available for a while, but most if not all of these do notprovide access to documents in a secure and protected manner or allowfor rapid location and retrieval of such files. Instead, the NAS devicesenable multiple computers to share the same storage space at once. Thus,these NAS devices implement a data-centric storage model but are moreconcerned about disk storage space availability than they are about filemanagement.

Enterprise content management (ECM) systems, on the other hand, providea formalized means of organizing and storing an organization's documentsand related content. ECM is an umbrella term covering documentmanagement, web content management, search, collaboration, recordsmanagement, digital asset management (DAM), work-flow management,capture and scanning.

Enterprise content management, as a form of content management, combinesthe capture, search, and networking of documents, usually together withdigital archiving, document management, and workflow. As part of ECMsystems, a document management system (DMS) is used to track and storeelectronic documents and/or images of paper documents, including aversioning capability (history tracking). The primary reason for a DMSover a file sharing system such as an NAS is to improve the sharing andauditing of business documents.

A problem is that as users continue to use their computer systems, thenumbers of files created, accessed, modified, and lost grows. Thebenefits of data file management systems are well known but many, if notmost, of the ECM document management systems are expensive, complicated,or both and most of the NAS devices are not adapted to provide truedocument management.

DRAWINGS

The various drawings supplied herein describe and are representative ofexemplary embodiments of the invention and are described as follows:

FIG. 1 is a schematic view of an exemplary system;

FIG. 2 is an exemplary browser view;

FIG. 3 is a schematic view of a first embodiment;

FIG. 4 is a schematic view of a second embodiment;

FIG. 5 is a schematic view of a third embodiment;

FIG. 6 is a box view of an exemplary message; and

FIG. 7 is an exemplary search view.

DESCRIPTION OF PREFERRED EMBODIMENTS

Referring to FIG. 1, system 1 comprises a network attached documentmanagement appliance, first computer 10, as well as second computer 20and local area network (LAN) 100 to which each of first computer 10 andsecond computer 20 are operatively connected. Each of first computer 10and second computer 20 further comprises a separate, immutable,queriable, unique identifier that can be used as a token, e.g. a CPUhardware ID or the like. In this way, first computer 10 has its ownunique token as does second computer 20.

First computer 10 comprises data store 15, database management software300, and, in some embodiments, server pipe service software 310. In mostconfigurations, first computer 10 further comprises preconfigureddatabase 12 (12 a, 12 b, 12 c) comprising a preconfigured set of tables13. Data store 15 is configured and adapted for storing files 17. Apredetermined portion of data store 15 is accessible only by softwareoperating in first computer 10 and may be further accessible to othersoftware, e.g. to software in second computer 20, using securityprovided by the operating system executing in first computer 10. Thatsecurity can also be used to further isolate and manage access to thepredetermined portion of data store 15 by software executing in firstcomputer 10. In certain embodiments, a portion of data store 15 may begenerally accessible and first computer 10 may act as a file server aswell as a document management system server. However, in each case, thepredetermined portion of data store 15 is still accessible only bysoftware operating in first computer 10 and still may be furtheraccessible to other software, e.g. to software in second computer 20,using security provided by the operating system executing in firstcomputer 10.

Second computer 20 comprises application software, e.g. word processorsand the like, and, in some embodiments, client pipe service software320. Access software is typically installed on second computer 20 wherethe access software is configured and adapted to communicate with firstcomputer 10 when a file operation is desired by second computer 20 withrespect to a file to be managed, as described herein below. As usedherein, second computer 20 may be a traditional computer such as adesktop or laptop computer; a tablet; a smart device such as a smartphone; or any other unit having a processor and display.

For embodiments that include it, server pipe service software 310 isoperatively in communication with database management software 300 andcan directly access data store 15. Server pipe service software 310 istypically adapted and configured to communicate over local area network100 using named pipe data transfer and operates server pipe 311 with apredetermined name such as one comprising the name of first computer 10.Similarly, client server service software 320 is adapted and configuredto be operatively resident in second computer 20 and to communicate overlocal area network 100 using named pipe data transfer to and with pipeserver service software 310. In most configurations, server pipe servicesoftware 310 is preconfigured with at least the token of first computer10 and server pipe name 313 and client server service software 320preconfigured with at least server pipe name 313.

In alternative embodiments, a process other than a pipe service may beused, e.g. an interprocess communication (IPC) server and clientincluding TCP/IP based communication servers/clients. These processesmay include distributed processes known as Component Object Model (COM)and/or distributed COM (DCOM), dynamic data exchange (DDE), remoteprocedure calls (RPC), and Windows Sockets as well as named pipes. As isknown to those of ordinary skill in these arts, some technologies suchas Windows Sockets may require having to assign a port for the localhost server.

In the operation of selected embodiments, still referring generally toFIG. 1, in general users of system 1 request a file operation to beperformed with respect to a managed folder and/or managed file 17. Thesefile requests typically comprise a request to store file 17 at orretrieve file 17 from first computer 10. The file operation request mayalso comprise obtaining data related to file 17 to be transferred priorto transferring file 17 to or from first computer 10 and associating theobtained data with file 17 to be transferred. If the file operationrequest involves storing file 17 at first computer 10, the fileoperation request operation typically includes storing all or a portionof the obtained data in a searchable record associated with file 17transferred in table 13 managed by database manager 300.

Each user may be further allowed to create a user taxonomy unique to theuser, typically a hierarchical taxonomy separate from a set of globalattributes. In these embodiments, each user may be allowed to associatea taxonomy member of the user taxonomy with either a desired managedfolder, a desired managed folder item, or both.

A set of preconfigured, related tables 13 are created in database 12which is managed by database manager 300. The set of related tables 13typically comprise data regarding each managed folder and each managedfolder item, e.g. a set of other folders and/or a set of files 17.Records may be added to set of related tables 13, where these recordscomprise data sufficient to identify the set of files 17 and/or otherfolder items having limited accessibility that are to be managed, e.g.file names, file types, client-matter identity associations, and thelike, or a combination thereof. A set of managed folders is isolatedfrom direct access by a user of the operating system of first computer10 and/or second computer 20, such as by using the security system ofthe operating system. Over time, the managed folders are populated bythe set of files 17 having limited accessibility that are to be managed.

A single physical file 17 may be designated as a linked file, in whichcase the same physical file can be made to appear to be associated witha set of folders, i.e. viewing the contents of Folder “B” may show thatit contains File “A” even though File “A” is really located in Folder“A.” A user with appropriate permissions may mark a file item as alinked file item, e.g. by having database manager 300 provide a linkedfile item attribute as part of the set of item attributes, and associatethe linked file item with a set of managed folders. This linked fileitem will then be displayed as a member of each associated member of theset of managed folders, provided view privileges allow such display. Adesired file operation may be performed against the linked file itemirrespective of the associated managed folder except that deletion ofthe physical linked file item is allowed only if it is associated with asingle managed folder.

A set of users can be created at system installation time but thecreation can be at any time before and/or after installation as well.Each user may be assigned a set of permissions where the permissions maycomprise a read permission, a write permission, a delete permission, amove permission, an import permission, an export permission, and a viewpermission, or the like, or a combination thereof, each of which can beto either allow the operation or deny the operation.

Referring additionally to FIG. 2, one way for a user to access themanaged folders and files 17 is via browser display 500 shown on displayscreen 21 (FIG. 1) at second computer 20 (FIG. 1), where browser display500 comprises a file item browsing form comprising folder panel 510 andfile panel 520. Folder panel 510 comprises a list of managed folders infirst predetermined portion 511 of browser display 500 and file panel520 comprises a list of contents of a currently selected managed folderof the list of managed folders, if any, in second predetermined portion522 of browser display 21. A user may select a managed folder visible infolder panel 510 to view a list of that managed folder's contents if theuser has appropriate permissions for that folder and may then be allowedto request a file operation on a selected file item 15 associated withthe selected managed folder, again if the user has appropriatepermissions for that file. In addition, a user may locate a managedfolder and/or file by using a searching form 600 (FIG. 7) which providessearch criteria entries.

In certain embodiments, a system manager and/or a user can create a linkor set of links to a client-matter related folder or subfolder. Thisshortcut can be presented to the user via an interface such as thebrowser interface in FIG. 2. In this manner, the user can rapidly accessfiles for which the user has adequate permissions as opposed to eithersearching using search 600 form or using a browser-like interface suchas browser form 500 to home in on those files.

Using either browser form 500 or search 600 form the user may optionallybe presented with a set of filtering criteria and the managed file itemsdisplayed in the file panel are limited to those which meet thefiltering criteria.

In any of these embodiments, data transfers between first computer 10and second computer 20 may involve encrypting the data to betransferred, e.g. using server pipe service token 312, client pipeservice software 320 token, or both as keys for encryption/decryption.The file operation may comprise a read request, a write request, adirectory request, a file information request, a delete request, or thelike, or a combination thereof. For example, the predetermined, specificfile operation may comprise a request to store file 17 at first computer10, and data related to file 17 to be stored at first computer 10 isobtained prior to transferring file 17 to first computer 10. Whether thedata are obtained at first computer 10 or second computer 20, theobtained data are associated with the file to be stored at firstcomputer 10 and stored in a searchable record associated with the fileto be stored at first computer 10 in one or more tables 13 managed bydatabase manager 300.

Additionally, data may be obtaining related to the data to betransferred prior to the data transfer and the obtained data associatedwith the data to be transferred. These obtained data may be stored in asearchable record associated with the data transferred in table 13 whichmanaged by database manager 300.

Upon successful complete of the data transfer, one or more tables 13controlled by database manager 300 are updated with a predetermined setof file data related to the data transfer. Updates of the data in tables13 may be controlled by database manager 300 by creating a new record intable 13 if the file data do not currently exist in table 13 or updatingan existing record which is associated with the file data in table 13with a predetermined set of data.

Once the file operation is successfully completed, for file creationsand/or updates first computer 10 can create file 17 with the file nameat predetermined file location using the received data. If table 13 isnot updated successfully or if file 32 is not created successfully,created file 17 is typically deleted.

In these various embodiments, text content, if any, may be extractedfrom the data in file 17 to be transferred and stored in a textsearchable record associated with the data transferred in table 13managed by database manager 300. These may be text that are associatedwith and/or embedded within file 17, e.g., a word processing,spreadsheet, presentation, email, or other files. The text content maybe extracted from the data to be transferred prior to or aftertransferring the data. If prior to, the extracted text content may bepart of in the data to be transferred. If after, text may be extractedat first computer 10 at one or more predetermined intervals.

In certain embodiments, the data to be transferred are encrypted by thesender, e.g. software executing in second computer 20, and decrypted bythe receiver, e.g. software executing in first computer 10, using serverpipe service token 312, client pipe service software 320 token, or acombination thereof as the encryption key or part of the encryption key.

In certain embodiments, managed folders, folder items, and their set ofitem attributes may be pre-existing and imported into system 1. Onceimported, these managed folders, folder items, and their set of itemattributes will no longer be accessible outside of first computer 10without using system 1.

A set of item attributes from a set of global item attributes may beassigned to one or more managed folders, e.g. user access rights,read-only attributes, defaults, and the like, or a combination thereof.Each managed folder item may then also be associated with a subset ofthe set of item attributes and a set of searchable attributes associatedwith each managed folder item. For example, a user might want to find aset of folders associated with a specific client-matter or a set offolders associated with a specific practice group area or other userdefined criterion.

Typically, a set of users is created during system installation such aswhen software modules (described below) are installed at second computer20. Each user will have predetermined access to a set of managed foldersand managed files. Each user may be assigned a set of permissions suchas a read permission, a write permission, a delete permission, a movepermission, an import permission, an export permission, and a viewpermission.

A user may be allowed to specify file versioning, either automaticallyor manually, where each version of a managed file comprises a physicallyseparate instance of the versioned managed file. Users with adequatepermission may also be allowed to specify where a versioned managed fileis to be stored, e.g. data store 15, a data store local to secondcomputer 20, a data store accessible over local area network 100, a datastore accessible over wide area network 200, or the like, or acombination thereof. Users with adequate permission may be allowed tofreeze a version of file 17, including a linked item version of file 17.If so desired, a new copy of the frozen file 17 is created with a newversion identified for file 17 and the new copy of file 17 associatedwith a selected managed folder.

Users with appropriate permission may specify a set of managed foldersor files for backup, including specifications of when and where backedup folders and files are to be stored, e.g. a data store local to secondcomputer 20, a data store accessible over local area network 100, a datastore accessible over wide area network 200, or the like, or acombination thereof. First computer 10 will then backup the foldersand/or files according to the schedule of file item backups.

A set of file operations is captured in an audit table 13 in database12. These may include requests for operations, actual operations (e.g.read, write, open, close, delete, move), and success/failure statusindicators. For example, database 12 is updated to reflect the status ofthe file operation, e.g. if it was successful or not.

Several differing embodiments will be described below, each of which mayfurther comprise one or more of the aspects described above.

Referring to FIG. 1 and FIG. 3, in a first embodiment files 17 may bemanaged on a file server such as first computer 10 by initiatingdatabase manager 300 at first computer 100 operatively in communicationwith a data network 100, where first computer 10 comprises data store 15which stores a set of files 17 having limited accessibility to secondcomputer 20 via data network 100. As will be known to those of ordinaryskill in these arts, data network 100 may comprise local area network100, wide area network 200, a virtual network, a telecom network, andthe like, or a combination thereof.

Files 17 may be made accessible to second computer 20, e.g. via datanetwork 100, only through the use of a predetermined, specific user nameand a predetermined, specific user password. The user name and userpassword are typically determined before an attempt is made to accessfiles 17. In an embodiment, the user name and user password aredetermined from a login form. In other embodiments, the user name anduser password are determined from either data within first computer 10and/or second computer 20, data accessible via data network 100 such asActive Directory information, or the like, or a combination thereof.

First computer 10 initiates server pipe service software 310, eitherautomatically after a triggering event, manually, or the like, or acombination thereof. Server pipe service software 310 is accessible,e.g. to second computer 20, over server named pipe 311 which comprisespredetermined server pipe name 313. In typical embodiments, databasemanager 300 and server pipe service software 310 are separate processesoperating in first computer 10.

Second computer 20 initiates client pipe service software 320, eitherautomatically after a triggering event, manually, or the like, or acombination thereof. Second computer 20 uses client pipe servicesoftware 320 to request a connection via server pipe service software310 to first computer 10 by using client pipe service software 320 toestablish a connection to server pipe service software 310 using servernamed pipe 311. In a preferred embodiment, establishing this connectioncomprises sending server pipe service software 310 message 400 (FIG. 6)which comprises client pipe service token 322 which is specific tosecond computer 20. In certain embodiments, a predetermined set of userrelated data may be appended to message 400 prior to its being sent,e.g. a user identifier and a file identifier. Moreover, the useridentifier may be required to be associated with sufficient permissionto access data associated with the file identifier as part of validatingthe received client pipe service token 322 against the predetermined setof valid tokens.

Client pipe service token 322 is received by server pipe servicesoftware 310 over server named pipe 311 and the received client pipeservice token 322 is then validated at first computer 10 against apredetermined set of valid client pipe service tokens 322. The receivedclient pipe service token 322 is typically validated at first computer10 by server pipe service software 310. The validation process mayinclude a query session between server pipe service software 310 anddatabase manager 300.

If received client pipe service token 322 is not validated, theconnection over server named pipe 313 is terminated for that requestfrom second computer 20. A subsequent request may be validated, eitherfrom second computer 20 or from another computer, depending on receiptof a valid client pipe service token 322.

If received client pipe service token 322 is validated by first computer10, first computer 10 sends server pipe service token 312 to client pipeservice software 320 over server named pipe 311, basically as an ACK,and waits for a further message 400 (FIG. 6) from client pipe servicesoftware 320. Client pipe service software 320 creates second pipe 321with a new predetermined second pipe name 323 where second pipe name 323is known to first computer 10, e.g. second pipe name 323 is based onand/or comprises client pipe service token 322. To help insure thatsecond pipe 321 is created and operational, second computer 20 maycreate message 400 comprising server pipe service token 312 and sendmessage 400 to server pipe service software 310 from client pipe servicesoftware 320 over either first pipe 311 or second pipe 321 to indicatethat second pipe 321 is ready for communication and that second computer20 is waiting for an acknowledgement message 400 from first computer 10.

An indication of whether client pipe service software 320 desires toobtain data from server pipe service software 310 or provide data toserver pipe service software 310 may be included as all or part ofmessage 400 (FIG. 6). When message 400 comprises a desire to providedata to server pipe service software 310, second computer 20 may provideserver pipe service software 310 with a file name to be used for file 17to be created at first computer 10 using the provided data as well asprovide server pipe service software 310 with data sufficient toidentify a location at first computer 10 at which to create file 17.This message may comprise various additional data, including, by way ofexample and not limitation, the length of the file to be sent to theserver so the server can verify it received all pertinent data.

Prior to creating file 17, first computer 10 may validate the file nameand the predetermined file location, and only allowing creation of file17 if the file name and the predetermined file location are validated.The validation may comprise a validation by server pipe service software310.

First computer 10 sends an acknowledgement message which, if the requestis to obtain a file, may comprise various additional data, including, byway of example and not limitation, the length of the file to be sent tothe client so the client can verify it received all pertinent data. Themessage may comprise a “begin transmission” or “begin reception” message400 (FIG. 6) sent to client pipe service software 320 from server pipeservice software 310 which, upon being received by client pipe servicesoftware 320, triggers second computer 20 to initiate the desired fileoperation over second pipe 321, e.g. a data transfer to or from firstcomputer 10. In this embodiment, all data are transferred using pipeI/O, but the messaging may be similar in more than this embodiment.

The predetermined, specific file operation may be trapped in a computerprogram operatively resident in second computer 20 when the computerprogram requests the predetermined, specific file operation, e.g. byadding software responsive to an event raised by the computer program toaccomplish the predetermined, specific file operation. For example,trapping may be accomplished by a software module integrated into atleast one of a computer operating system or the computer programresponsive to an event raised by the computer program to accomplish thepredetermined, specific file operation.

If the data transfer is completed successfully, the transferringcomputer sends a successful transfer message 400 (FIG. 6) between serverpipe service software 310 and the client pipe service.

Referring now to FIG. 1 and FIG. 4, in a second embodiment files 17accessible to a computer operating system are managed by isolating a setof managed folders at first computer 10 from direct access by a user ofsecond computer 20. These managed folders comprise a set of managedfiles 17 associated with the managed folders, where the set can beempty. A set of item attributes may be assigned from a predetermined setof global item attributes to each managed folder and each managed folderpopulated with a set of managed folder items which may comprise files17, folders, links to files 17 and/or folders, or the like, or acombination thereof. These item attributes may comprise read access,write access, deletion access, move access, export access, and the like,or combinations thereof. Each managed folder item may also be associatedas well with a subset of the set of item attributes and with a set ofsearchable attributes for each managed folder item.

A software module is integrated into a software application at secondcomputer 20, e.g. a word processing or email software application, andhooks into a predetermined set of software application events, allowingthe file operation if the user has appropriate permissions to performthe file operation by trapping a file operation request made by thesoftware module at second computer 20 to effect the file operation atthe software application event level. The access software is adapted andconfigured to selectively and temporarily map the predetermined portionof data store 15 as temporary link 25 when the file operation is desiredby second computer 20 with respect to a file to be managed. For example,the access software can set a logical route to a predetermined folder orset of folders resident in data store 15 and map that logical route to adrive designator, e.g. the “N:” drive, as temporary link 25.

If it is verified that the user has appropriate permissions to performthe desired file operation, a temporarily enabled secured logical pathto first computer 10, temporary link 25, is created from second computer20 and the file operation allowed over temporary link 25 to firstcomputer 10, e.g. a temporary mapping of a predetermined folder at firstcomputer 10 to a logical drive designator, e.g. “N:”. Upon completion ofthe requested operation, temporary link is dissolved or otherwiseremoved.

In certain embodiments, creation of temporary link 25 comprisesinitiating server pipe service software 310 at first computer 10, whereserver pipe service software 310 is accessible over predetermined servernamed pipe 311. Server pipe service software 310 may be initiated on amore-or-less permanent, on demand, and/or periodic basis. Client pipeservice software 320 is initiated at second computer 20, typically ondemand, and a connection to first computer 10 by second computer 20 isrequested by using client pipe service software 320 to establish aconnection to server pipe service software 310 using server named pipe311. Establishing this connection typically comprises sending message400 (FIG. 6) comprising client pipe service token 322 to server pipeservice software 310; receiving message 400 from client pipe servicesoftware 320 by server pipe service software 310; validating thereceived client pipe service token 322 at first computer 10 against apredetermined set of valid client pipe service tokens 322 typicallycreated during system installation; and allowing creation of temporarylink 25 only if the received client pipe service token 322 is validated.

In a version of this embodiment, a software application executing insecond computer 20 first queries database manager 300 to determine ifsecond computer 20 has adequate permission to perform a predetermined,specific file operation with respect to a file that is a member of theset of files having limited accessibility. If second computer 20 hasadequate permission, second computer 20 initiates temporary link 25 tothe set of files 17 having limited accessibility when the predetermined,specific file operation is requested at second computer 20.

Once temporary link 25 is established, second computer 20 performs thepredetermined, specific file operation and software operative in eitheror both of first computer 10 and/or second computer 20 updates table 13managed by database manager 300 with the completed status of thepredetermined, specific file operation. In this embodiment, filetransfers occur over temporary link 25 such as by using operating systemfile transfer methods.

Whether or not successful, upon completion of the predetermined,specific file operation, second computer 20 terminates temporary link25.

Referring now to FIG. 1 and FIG. 5, in a third embodiment, as opposed tothe methods described above driver-based disk mapper 326 is initiated atsecond computer 20, where driver-based disk mapper 326 creates a mappedpseudo-disk drive 26 at second computer 20. For example, the user (and,by implication, software operative in second computer 20) may see drive“N:” at second computer 20 and the software executing in second computer20 may operate as if drive “N:” is a physical drive, but drive “N:” isonly accessible via driver-based disk mapper 326 to emulate a physicaldrive, e.g. mapped pseudo-disk drive 26.

Software executing at second computer 20 attempts a file operation on afile 17 of the set of files 17 having limited accessibility at secondcomputer 20 via pseudo-disk drive 26, e.g. attempts to open file 17.Upon receipt of the file operation request, driver-based disk mapper 326connects to server pipe service software 310 to establish whether or notsecond computer 20 is a valid, registered computer using message 400(FIG. 6) which comprises client pipe service token 322. If secondcomputer 20 is a valid, registered computer, driver-based disk mapper326 queries database manager 300 to determine if second computer 20 hasadequate permission to perform the specific, requested file operationwith respect to file 17 of the set of files 17 having limitedaccessibility. If second computer 20 has adequate permission,driver-based disk mapper 326 allows the completion of the specificrequested file operation between first computer 10 and second computer20 via pseudo-disk drive 26, e.g. using computer operating system filetransfer methods.

As opposed to the other methods described herein, pseudo-disk drive 26is not temporary link 25 and allows for files 17 to be managed withouthaving a software module integrated into an application at secondcomputer 20. Thus, if a software module integrated into an applicationat second computer 20 does try to open a managed file 17 usingpseudo-disk drive 26, that software module can identify itself topseudo-disk drive 26, e.g. via a token or other message, and pseudo-diskdrive 26 can then let the software module access managed file 17 asdescribed herein. If, however, a file operation request is made throughpseudo-disk drive 26 from other than a software module that is part ofsystem 1, pseudo-disk drive 26 can present one or more forms to the userat second computer 20 to gather information required by system 1 formanaged files, e.g. file description data, user description data, andthe like. Pseudo-disk drive 26 can then perform many if not all of thefunctions required, as described herein, which normally would beperformed by the software module that is part of system 1.

Further, as will be understood by those of ordinary skill in thesoftware and computer networking arts, because pseudo-disk drive 26represents a logical path, it can provide a secure path to so-calledCloud resources, e.g. servers 10 accessible over the Internet.

As with the other embodiments, table 13, managed by database manager300, is updated with the completed status of the specific fileoperation.

As should be apparent to those of ordinary skill in the computersoftware arts, table 13 may be one or more tables 13; database 12 may beone or more databases 12 a, 12 b, 12 c; file 17 may be an unmanaged fileor a managed file, as context dictates (although usually file 17indicates a managed file herein); and folder may be one or more foldersor subfolders.

Further, rather than used named pipes, as mentioned above otherprocesses may be substituted such as DCOM servers/clients and WindowsSockets servers/clients.

It will be understood that various changes in the details, materials,and arrangements of the parts which have been described and illustratedabove in order to explain the nature of this invention may be made bythose skilled in the art without departing from the principle and scopeof the invention as recited in the appended claims.

What is claimed is:
 1. A method of managing files on a file server,comprising: a. initiating a database manager at a first computeroperatively in communication with a data network, the first computercomprising a data store and a first unique identifier, the data storecomprising a set of files accessible to a second computer alsooperatively in communication with the data network via the data network;b. initiating a server pipe service at the first computer, the serverpipe service creating a server named pipe which is accessible using apredetermined server pipe name; c. initiating a client pipe service atthe second computer, the second computer comprising a second uniqueidentifier; and d. requesting a pipe connection between the firstcomputer and the second computer by using the client pipe service toestablish a connection to the server pipe service using the server namedpipe, establishing the connection comprising: i. sending the server pipeservice a first message comprising a client pipe service token specificto the second computer; ii. receiving the first message by the serverpipe service; iii. validating the received client pipe service token atthe first computer against a predetermined set of valid client pipeservice tokens; iv. terminating the server pipe connection if thereceived client pipe service token is not validated; v. if the receivedclient pipe service token is validated by the first computer,
 1. sendinga second message comprising a server pipe service token to the clientpipe service over the server named pipe;
 2. creating a second pipecomprising a predetermined second pipe name by the client pipe service,the second pipe name known to the first computer;
 3. creating a thirdmessage comprising the server pipe service token at the second computer;4. sending the third message to the service pipe service from the clientpipe service over the second pipe;
 5. sending a fourth message to theclient pipe service from the server pipe service to acknowledge receiptof the third message and to indicate that the server pipe service isready for a further file operation using the second pipe;
 6. receivingthe fourth message by the client pipe service;
 7. initiating the fileoperation between the first computer and the second computer over thesecond pipe;
 8. when the file operation is completed, sending a fifthmessage between the server pipe service and the client pipe service, thefifth message comprising a status indicator indicating whether or notthe data operation was completed successfully; and updating a record ina table controlled by the database manager with a predetermined set offile data related to the requested file operation, the set of file datacomprising the status indicator.
 2. The method of claim 1, furtherwherein the received client pipe service token is validated at the firstcomputer by the server pipe service, the validation comprising queryingthe database manager.
 3. The method of claim 1, further comprising: a.appending a predetermined set of user related data to the first message,the predetermined set of user related data comprising a user identifierand a file identifier; and b. requiring the user identifier to beassociated with permission to access data associated with the fileidentifier as part of validating the received client pipe service tokenagainst the predetermined set of valid tokens.
 4. The method of claim 1,wherein updating the table controlled by the database manager with thepredetermined set of file data related to the requested file operationfurther comprises: a. creating a new record in the table to contain thepredetermined set of file data if the file data do not currently existin the table; and b. updating an existing, matching record in the tablewith the predetermined set of data if the file data do currently existin the table.
 5. The method of claim 1, further comprising including, inthe first message, an indication of whether the client pipe servicedesires to obtain data from the server pipe service or provide data tothe server pipe service.
 6. The method of claim 5, further comprising,for a first message comprising a desire to provide data to the serverpipe service: a. providing the server pipe service with a file name tobe used for a file to be created at the first computer using theprovided data; b. providing the server pipe service with data sufficientto identify a location at the first computer at which to create thefile; c. creating the file with the file name at the predetermined filelocation using the received data; and d. if the table is not updatedsuccessfully, deleting the created file.
 7. The method of claim 6,further comprising, prior to creating the file: a. validating the filename at the first computer; b. validating the predetermined filelocation at the first computer; and c. only allowing creation of thefile if the file name and the predetermined file location are validated.8. The method of claim 6, further comprising, as part of validating thefile name and file location: a. appending a predetermined set of userrelated data to the first message, the predetermined set of user relateddata comprising a user identifier and a file identifier; and b.requiring the user identifier to be associated with permission to createthe file having the file name at the file location.
 9. The method ofclaim 1, wherein the database manager and the server pipe service areseparate processes operating in the first computer.
 10. The method ofclaim 1, further comprising: a. obtaining data related to the data to betransferred prior to the data transfer; b. associating the obtained datawith the data to be transferred; and c. storing the obtained data in asearchable record associated with the data transferred in a tablemanaged by the database manager.
 11. The method of claim 1, furthercomprising: a. extracting text content from the data to be transferred;and b. storing the extracted text content in a text searchable recordassociated with the data transferred in a table managed by the databasemanager.
 12. The method of claim 11, further comprising: a. extractingtext content from the data to be transferred prior to transferring thedata; and b. embedding the extracted text content in the data to betransferred.
 13. The method of claim 1, further comprising encryptingdata transferred as a result of the requested file operation using atleast one of the server pipe service token or the client pipe servicetoken as a part of an encryption key.
 14. The method of claim 1,wherein: a. the server pipe service token comprises the first uniqueidentifier; and b. the client pipe service token comprises the secondunique identifier.
 15. A system for managing files over a network,comprising: a. a first computer operatively in communication with a datanetwork, the first computer comprising: i. a data store; ii. a firstunique identifier; iii. database management software operationallyresident in the first computer; and iv. server pipe service softwareoperationally resident in the first computer, the server pipe servicesoftware configured and adapted to communicate over a predeterminedserver named pipe and a dynamically created client named pipe; b. asecond computer, the second computer comprising: i. a second uniqueidentifier; ii. client pipe service software operationally resident inthe second computer, the client pipe service software configured andadapted to:
 1. communicate with the server pipe service software overthe predetermined server named pipe;
 2. communicate with the server pipeservice software over the dynamically created client named pipe; andprovide an interface to the client pipe service to application softwareoperationally resident in the second computer; and iii. a softwaremodule accessible to the application software, the software moduleadapted and configured to communicate with the client pipe servicesoftware and with the database management software to effect a desiredfile operation.
 16. The system of claim 15, wherein the data networkcomprises at least one of a local area network or a wide area network.17. The system of claim 15, wherein the software module is furtheradapted and configured to be integrated into the application software.18. The system of claim 15, wherein initial elements of the databasemanagement software, the server pipe service software, and the clientpipe service software are preconfigured.